Release 10.1A: OpenEdge Getting Started:
OpenEdge Reference Architecture

Components of the Integration Layer

Similar to the Presentation Layer (see Chapter 4 "Presentation Layer"), the Integration Layer commonly employs three component types. The three types of component are shown in Table 5–2.

Table 5–2: Integration Layer components

Component type	Role
Adapter	Receives data and does any necessary data conversion (such as EDI to JMS format). Passes context information (such as user ID) to Controller components.
Controller	Enforces security rules and interprets context information. Routes the request to the appropriate Processor component.
Processor	Services the request and returns information.

The following sequence occurs when the Integration Layer receives a request:

A request from an external system comes into the Adapter component.
The Adapter component passes the information to the Controller component.
The Controller component then routes the request to the appropriate Processor component.
The Processor component works through the service interfaces that are exposed by the Business Servicing Layer to complete the required tasks. (See the "Service interfaces" section for more information.)
Note: By separating the tasks of connection and conversion (the role of the Adapter component) from the tasks of translation, process flow and processing (the role of the Processor component), one Processor component can serve the needs of multiple adapters.

Properties of Integration Layer components

As is the case with other components throughout the OpenEdge Reference Architecture, properties of components within the Integration Layer are typically used to hold instance information relating to the component at run time. Properties could include a unique ID, configuration information, or authentication information.

Routines of Integration Layer components

The routines commonly designed to support Integration Layer components vary by the type of component and relate to the tasks that they must perform. The table below lists some common routines for Integration Layer components, organized by component type.

Table 5–3: Common routines of Integration Layer components

Component type	Common routines
Adapter	Events. For example, the connection events that occur when connecting to a requester or to a Controller component. Process. For example, the transfer of converted information to the Processor component.
Controller	Authentication. For example, a login routine that communicates with an Authorization Controller component. Any routines that direct the actions of other Integration Layer components.
Processor	Translation. For example, manipulation of data related to mapping. Process. For example, passing data to components in the Business Servicing or Data Access Layer for further actions.